home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d20
/
fdhm210.arc
/
FDHM.DOC
next >
Wrap
Text File
|
1991-09-27
|
26KB
|
703 lines
▒▒▒▒▒▒▒█ ▒▒▒▒▒▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█
▒▒▒█▀▀▀▀ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒▒ ▒▒▒▒█
▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒▒▒▒▒▒▒▒█
▒▒▒▒▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒▒▒▒▒▒▒▒█ ▒▒▒█▒▒█▒▒▒█
▒▒▒█▀▀▀▀ ▒▒▒█ ▒▒▒█ ▒▒▒█▀▀▀▒▒▒█ ▒▒▒█▀▀▀▒▒▒█
▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█
▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█
▒▒▒█ ▒▒▒▒▒▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█ ▒▒▒█
▀▀▀▀ ▀▀▀▀▀▀▀▀▀ ▀▀▀▀ ▀▀▀▀ ▀▀▀▀ ▀▀▀▀
FrontDoor History Manager
Version 2.10
International
Copyright (c) 1990/91 by Ulrich Bartelt
Table of contents:
Licensing Information 2
What it does 3
Points 3
Where to install ? 4
Command mode 4
Setup 6
Timezones 7
Phonetable 9
Inbound Costs 10
Cleaning 10
Transfer History 11
Graphics 11
Reports 12
Files 13
Multitasking 13
Germany and the rest of the World 14
Regards 14
FrontDoor History Manager Vers. 2.10 page - 2 -
┌───────────────────────┐
│ Licensing Information │
└───────────────────────┘
FDHM is the copright material of Ulrich Bartelt. It may only be
used in accordance with the conditions set in the following
license agreement:
- You may use FDHM for a period of four weeks on a trial basis
in order to determinate it's suitability for your particular
application. After this period you MUST register FDHM.
- Group registrations are available, and are dealt with on a
case by case basis.
- Registration entitles you to use FDHM and any future versions
of FDHM for as long as you wish, subject to any special
licensing conditions attaches to future versions. For details
on the registering procedure, refer to the contens of the
special file REGISTER.DOC included in this packet.
- Ulrich Bartelt is in no way obligated to provide future
versions of, or support for, FDHM.
- You may not modify or otherwise reverse-engineer FDHM.
- You are encouraged to distribute FDHM provided that no fee is
charged for its distribution, and that the distribution
archive is not modified in any way. Pay-Bulletin-Board-
Systems may however charge their normal fee, provided that no
additional charge is levied for FDHM.
- FDHM may not be included as part of any software library
which is distributed on a registered basis without prior
written permission of Ulrich Bartelt. This expecially
includes all kinds of shareware distribution libraries.
FrontDoor History Manager Vers. 2.10 page - 3 -
┌──────────────┐
│ What it does │
└──────────────┘
One of the great advances of FrontDoor 2.00 and much more of
FrontDoor 2.01 is the extended information in its history-files.
From FD 2.00 and above the connect time of outbound calls is
posted to OUTBOUND.HIS. From FD 2.01 and above also the
connectiontime of incoming calls is posted to INBOUND.HIS. That
makes it possible to calculate the exact costs of a call by the
time FrontDoor writes to this files.
To calculate the costs with FDHM it is recommended that you have
to pay your phonebill on a unit base system !!!
If you are running a timebased system where you have to pay a
fixed rate for every minute you can properly take the costs from
your nodelist set-up. Although you can also use FDHM but never run
FDHM POST (see below).
With FDHM you will have full access to the history files of
FrontDoor. You can browse and edit them and FDHM will show you a
lot of information normally not in this files. More than that, if
you make changes and calculate the costs you can also see the
changes in FrontDoor by pressing alt-o and alt-i.
Normally you will only keep your FrontDoor historyfiles for a
short period, say 14 days. And you cannot make a difference in
keeping inbound and outbound. With FDHM you can.
FDHM is using its own history files named SAVEIN.HIS and
SAVEOUT.HIS. These files are 5 time shorter than the original
files. So it should be possible to hold the history of a complete
year on your harddisk. F.e. the inbound file on my system with
7000 entries for a period of 160 days only take 150 KB of
diskspace.
┌────────┐
│ Points │
└────────┘
Normally, points should have very low or completely non incoming
traffic. You can tell FDHM that your system is a pointsystem.
FrontDoor History Manager Vers. 2.10 page - 4 -
┌────────────────────┐
│ Where to install ? │
└────────────────────┘
FDHM must find SETUP.FD either in the directory you invoke it or
in the directory the environment string FD points to. FDHM looks
for the following files:
INBOUND.HIS
OUTBOUND.HIS
PASSWORD.FD
On startup, FDHM first searches for the inbound files. If not
found all functions which depends on these files are disabled.
NOTE: FDHM expected all paths in SETUP.FD to include a drive.
┌───────────┐
│ Two Modes │
└───────────┘
FDHM has two modes:
1. Fullscreen mode
You will find the fullscreen mode looking similar to FrontDoors
set-up program. This way I don't have to say any word on using it.
If you already have set-up FrontDoor you will feel familiar with
FDHM.
2. Command mode
Syntax: FDHM <keyword> [options]
valid keywords are:
POST will calculate the exact costs based on your
costtable and post them into FrontDoors history
files.
PACK all new entries in FrontDoor files not already in
the FDHM files are copied. DO *NOT* change the
timestamp of the *SAVE* files. You will see that
the timestamp represents the last entry prozessed
in the FrontDoor files.
DAYREP write out a daily report. Without options, FDHM
will take the actual day. The default filename is
TREPORT.TXT
Options: -t<days>
Example: -t1 will write the report
for yesterday.
-f<filename>
FrontDoor History Manager Vers. 2.10 page - 5 -
MONTHREP write out a monthly report. Without options, FDHM
will write a report for the actual month. The
default filename is MREPORT.TXT
Options: -m<months> difference in months
Example: -m5 will write the report for the month 5
month before now. If this was in the last
year FDHM will take it in account.
-f<filename>
You can combine all options on one line with the exception that -f
is valid for the last report file.
Though it's possible to write:
FDHM POST PACK MONTHREP DAYREP -t1 -fyesterd.rep
It is recommended to run FDHM POST PACK once a day !!!
FrontDoor History Manager Vers. 2.10 page - 6 -
┌───────┐
│ Setup │
└───────┘
Setting up FDHM should normally be done in less than 10 minutes if
you follow the instructions given below.
Defaults:
─────────
Address a network address taken for the default input on
every place you have to enter addresses. This
should allow you to use short form input where f.e.
1 will be replaced with zone:net/1
Unit the costs of one unit
Overlay modems with MNP require a short time to figure out
if the other end can also use MNP. While this time
is not honoured by the CONNECT message you can set
it up here. 3-5 seconds should be a good value for
a HST modem.
Mydefault default timezone for nodes in your own zone. If you
keep your SAVE-files for a long period, like I do,
you will see that some nodes are lost in time.
Normally you will use the replace function for
nodes close to you if a nodenumber has changed.
Othdefault default timezone for node in foreign zones
SaveDay default inputvalue for cleaning the FDHM files
FDDays default inputvalue for cleaning the FrontDoor
history files
RegNo. your registration number
Swapping wether or not FDHM should swap itself to disk or
EMS when doing any shell.
EMS/Disk Define, if FDHM should use EMS or disk if swapping.
FrontDoor History Manager Vers. 2.10 page - 7 -
┌────────────┐
│ Timezones │
└────────────┘
You can enter up to 20 timezones. This should be the first thing
you do 'cause these timezones are also need to properly set-up the
FDHMNODE.CTL file.
Name a string that represents the name of the zone. This
string will be shown if you look at an entry of
your history files.
Low the time in seconds you can call for ONE unit if
phonerates are cheap. F.e. this is 720 for Germany
while you can phone 12 minutes with one unit.
High same as before but for expensive rates
see the below example of how to set-up for the Netherlands:
╒═══════════════════════════════════[ Timezones ]═╕
│ 1 Local 600.00 300.00 │
│ 2 Border Rate 25.00 25.00 │
│ 3 National 94.00 47.00 │
│ 4 International A 8.20 8.20 │
│ 5 International B 10.50 8.20 │
│ 6 International D 6.40 6.40 │
│ 7 International E 7.80 6.40 │
│ 8 International F 5.00 5.00 │
│ 9 International G 3.70 3.70 │
│ 10 International H 4.00 3.50 │
│ 11 International I 4.00 3.50 │
│ 12 International J 2.60 2.15 │
│ 13 International K 2.60 2.15 │
│ 14 International L 1.55 1.55 │
│ 15 International M 1.85 1.55 │
│ 16 International N 1.85 1.55 │
│ 17 International O 0.50 0.50 │
└─────────────────────────────────────────────────┘
FrontDoor History Manager Vers. 2.10 page - 8 -
┌───────────┐
│ Timetable │
└───────────┘
For each timezone you get an extra window to set-up the times in a
day where phonecosts are cheap or expensive. See the below
examples that are corresponding with the above table:
Local
╒════════════════[ Timetable ]═╕
│ 0 12 23 │
│ ┌───────────┬──────────┐ │
│ So XXXXXXXXXXXXXXXXXXXXXXXX │
│ Mo XXXXXXXX----------XXXXXX │
│ Tu XXXXXXXX----------XXXXXX │
│ We XXXXXXXX----------XXXXXX │
│ Th XXXXXXXX----------XXXXXX │
│ Fr XXXXXXXX----------XXXXXX │
│ Sa XXXXXXXXXXXXXXXXXXXXXXXX │
│ │
│ X = cheap - = expensive │
╘═════════════════════════════════╛
International B
╒══════════════════[ Time Table ]═╕
│ 0 12 23 │
│ ┌───────────┬──────────┐ │
│ So --XXXX------------------ │
│ Mo --XXXX------------------ │
│ Tu --XXXX------------------ │
│ We --XXXX------------------ │
│ Th --XXXX------------------ │
│ Fr --XXXX------------------ │
│ Sa --XXXX------------------ │
│ │
│ X = cheap - = expensive │
╘═════════════════════════════════╛
International N
╒══════════════════[ Time Table ]═╕
│ 0 12 23 │
│ ┌───────────┬──────────┐ │
│ So XXXXXXXXXXXXXXXXXXXXXXXX │
│ Mo XXXXXXXXXX------------XX │
│ Tu XXXXXXXXXX------------XX │
│ We XXXXXXXXXX------------XX │
│ Th XXXXXXXXXX------------XX │
│ Fr XXXXXXXXXX------------XX │
│ Sa XXXXXXXXXXXXXXXXXXXXXXXX │
│ │
│ X = cheap - = expensive │
╘═════════════════════════════════╛
FrontDoor History Manager Vers. 2.10 page - 9 -
Phonetable:
───────────
Unlike previous versions, FDHM does a phonenumber matching now.
The first thing you have to do is to build up a controlfile for
the FDHMNode nodelist compiler that comes with this packet. Set-up
your zones and Regions for the 'Timetable' you already should have
defined. The controlfile and more then that also all nodelists
should be placed in the directory which is defined as 'Nodelist'
in your FrontDoor set-up.
Now run FDHMNODE.
After that, 99% of your cost set-up is ok.
Your only have to set-up thouse nodes not attached by the
FDHMNODE.CTL files. This would normally be the nodes locally to
you or thouse that does not match the same costs as for your
region.
Here is an example for the 1% that is left over:
49-2590 far
49-202 Regional
49-203 Regional
49-211 Regional
49-259 Regional
.....
49-231 Local
49-233 Local
29-234 Local
.....
If you have a good look at the information that comes from your
PTT you may save a lot of entries in the manager. For example if
you have 8 predials defined as regional and only 2 for far, you
can set-up thouse 2 for far and the rest in one entry for
regional. Example:
49-2591
49-2592
49-2593
...
49-2599
are all regional. only 49-2590 is far. So I define this entry
as far, and all others as regional leaving away the last
digit.
Everytime you leave the nodemanager all entries are sorted in the
form: timezone - phonenumber.
A good way to see if your set-up is complete, is to got to the
history files of FrontDoor and look if the timezone is listed when
you press enter on various entries.
FrontDoor History Manager Vers. 2.10 page - 10 -
┌─────────────────┐
│ Inbound Costs ? │
└─────────────────┘
It should be clear, that there are no real costs for your inbound
mail traffic. The costs listed in the inbound files are the costs
of the caller, not yours. This way you have a good overview how
much money your phonecompany makes with your system. And if you
can follow the costs for a special node, you can take over to send
the mail to this node if he is paying you the phonebill. This is a
good way if someone is on vacation and does not want to make his
system outgoing calls.
┌──────────┐
│ Cleaning │
└──────────┘
FDHM allows you to clean-up every history file separately. Unlike
in FrontDoor you can manage to get the same size for both
FrontDoor files. F.e. I'm normally running my FD under Desqview in
a small window. Everytime I invoke the internal manager of
FrontDoor it tells me that there is not enough memory to load the
entire inbound file. Running FDHM PACK every day, I can set
FrontDoor's 'days to keep history' to a very short value that
allows me to look at the complete inbound file.
In order to make life easier FDHM will insert the values from the
defaultentries if you invoke an option.
Replacing: To prevent miscalculation if a nodenumber changes
during a period of calculation you can replace the
old nodenumber with the new one.
FrontDoor History Manager Vers. 2.10 page - 11 -
┌──────────────────┐
│ Transfer History │
└──────────────────┘
The contents of 'LASTCALL.FD' are written to a file TRANSFER.HIS
in your FrontDoor system-directory when you invoke FDHM PACK. FDHM
takes care to update TRANSFER.HIS only once a day, so you can run
PACK as often as you want. While every record in TRANSFER.HIS has
only 28 bytes it will take a very long time to fill your harddisk.
FDHM will take the information from 'Yesterday' to update
TRANSFER.HIS.
┌──────────┐
│ Graphics │
└──────────┘
The information of your inbound and outbound mailusage is held in
two files called INUSAGE.BBS and OUTUSAGE.BBS. Everytime you
invoke Pack from FDHM or from the commandline these files are
updated. When you invoke 'Graphics' inside FDHM you will notice
that the graphics are immediately shown. Previously FDHM had to
read the complete Savefiles to build up the graphics.
FDHM will not write any textfiles *.ASC any longer! Instead you
find a separate program FDHMGRAF.EXE in the distribution packet
that does this job. It writes out MAILIN.ASC and MAILOUT.ASC and
in addition to this already known files also MAILIN.ANS and
MAILOUT.ANS The purpose of this files is, to show them to a bbs-
user however you can take the *.ASC files and post them in a
message.
NOTE: When you upgrade from FDHM 2.00, there are no *USAGE.BBS
files on your harddisk. Please run INITGRAF.EXE to build
them up. You can delete INITGRAF.EXE after its first and
last run.
Programmers:
If you like to write your own usage graphic: Both *.BBS are
nothing more than an Array[0..23] of LongInt. For every hour the
usagetime in seconds is posted in this array.
FrontDoor History Manager Vers. 2.10 page - 12 -
┌─────────┐
│ Reports │
└─────────┘
To prevent FDHM to write out the statistics for inbound calls you
can set-up FDHM into 'Pointmode'. Go to 'Set-up-Defaults' and
enter an address with a pointnumber. You will see [Pointmode] now
in this window. To change back, just press enter twice on the
address.
Note: Listing a period means listing a time between two dates.
So a complete month will be the time from the firth day
in that month to the first day in the next month. The
startdate is included, the enddate *NOT*.
The central function in the reports section is the 'Period'
function. If you don't give any address the transfer of all
connections is taken in account. If you enter a address *or* a
part of a address the string you entered will be compared with a
string that is build from the addresses in the savefiles. This is
a *very* powerful function. See some examples what you can make
with it:
You enter:
2: will list all connections with zone 2
2:241/ will list all connections with zone 2, net 241
.15 will list all connections with points of the number
15. Not very useful, but it works.
2:241/5800. will list all connection with 2:241/5800 *and* all
points of this system
2:241/5800.0 will only list this special system.
5800.0 same as above if there are no other nodes 5800.0
from other nets.
One word about the dateformat. FDHM will get the format of dates
and times directly from DOS. If you have no country information in
you CONFIG.SYS file, DOS defaults to the American 'mm/dd/yy'
format. FDHM will also do so. So entering dates and times should
ever be in the same format as if you enter DATE or TIME on the
DOS-comandline.
FrontDoor History Manager Vers. 2.10 page - 13 -
┌───────┐
│ Files │
└───────┘
There is a internal editor ( yes it's BinEd) in FDHM to edit or
show the following files on the fly:
- your logfile
- ROUTE.FD
- NAMES.FD
- FDNODE.CTL
o list of magic filenames
o security list of magic names
o normal request list
o security request list ( FD 2.01 only)
o bannerfile
o eventfile
o failed request file
If you have not set-up one of the files marked with 'o' the menu-
option will be disabled.
NOTE: If you touch ROUTE.FD (even if you don't change
anything) with FDHM, the file will get a new timestamp.
This will cause FrontDoor to do a rescan.
┌──────────────┐
│ Multitasking │
└──────────────┘
Both FDHM and FDHMNODE are clever enough to handle its files when
you run a multitasker like Desqview. All files needed by FDHM only
for reading are opened in Readonly modus. So you can run FrontDoor
or RA in one window and FDHM in the other. You can also compile a
new index with FDHMNODE while FrontDoor is running.
But you have to take care of the situation when editing a file
with FDHM and another program wants to get access on that file
that cannot detect that it only needs reading. F.e. if your
editing ROUTE.FD with FDHM, FrontDoor will failed to open that
file if a transfer comes in.
FDHM has a special support for multitasking systems that will give
time to other tasks if it only waits for a keystroke.
FrontDoor History Manager Vers. 2.10 page - 14 -
┌───────────────────────────────────┐
│ Germany and the rest of the World │
└───────────────────────────────────┘
This version of FDHM is *NOT* for Germany however you can set-up
it to run in Germany. You can save a lot of time if you request
FDHMGER from 2:241/5801 and get the special version in the German
language. The German version and the international version are
incompatible! You can't replace one with each other.
┌─────────┐
│ Regards │
└─────────┘
I would like to thank all people for there suggestions to make
FDHM what it is now. Exspecially thouse people who registered the
very first version and helped me in this way to fight against
myself and continue the work.
A special thank also to Peter Janssens of 2:512/1 who tested this
program in a country that has not this very easy phonesystem like
germany. FDHMNODE.CTL and the examples for set-up are from Peter.